fixed bogus formatted .properties file

…ings (as per the standard)

Add a unit test, refactor #encodeKey: messages a bit

Add NeoJSONFloatPrinter as a first custom implementation with fixed parameters (for now)
Add NeoJSONFloatPrinterTests
Add NeoJSONWriterTests>>#testFloatPrinter

Add #lowPrecision and #scientificOnly as examples with unit tests.

This is meant as a convenience feature only as the official JSON specification clearly states "An object is an unordered set of name/value pairs".

…o 7 & 8, but fixed in Pharo 9 and later) by adding the correct implementation to NeoJSONObject

…line setting

Add Pharo 10 to CI

 - Checking if SmallTime class is available, if yes use it, if no
   stick to the standard one
 - Making the test work with 24-hour or 12-hour format

In Pharo IdentityDictionary is a subclass of Dictionary, but in
GemStone it is a KeyValueDictionary.  Need to create method to get
correct results.

In Pharo String is a subclass of Arraycollection, but in
GemStone it is CharacterCollection.  In case MultiByteString is used
we need to have neoJsonOn: for those too.

To quote RFC8259, which defines JSON format:

An object is an *unordered* collection of zero or more name/value
pairs, where a name is a string and a value is a string, number,
boolean, null, object, or array.